home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
internet-drafts
/
draft-ietf-frnetmib-fr-01.txt
< prev
next >
Wrap
Text File
|
1993-07-08
|
64KB
|
2,066 lines
Internet Draft Frame Relay Service MIB July 2, 1993
Definitions of Managed Objects
for Frame Relay Service
July 2, 1993
Frame Relay Service MIB Working Group
Tracy A. Brown (editor)
Bell Communications Research
331 Newman Springs Road
Red Bank, NJ 07701
tacox@mail.bellcore.com
1. Status of this Memo
This document is an Internet Draft. Internet Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet
Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted
by other documents at any time. It is not appropriate to use
Internet Drafts as reference material or to cite them other
than as a "working draft" or "work in progress."
Please check the I-D abstract listing contained in each
Internet Draft directory to learn the current status of this
or any other Internet Draft.
2. Abstract
This memo defines an extension to the Management Information
Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, it defines objects for
managing the Frame Relay Service.
This memo does not specify a standard for the Internet
community.
T. Brown (editor) Expires 1/2/94 [Page 1]
Internet Draft Frame Relay Service MIB July 2, 1993
3. The Network Management Framework
The Internet-standard Network Management Framework consists of three
components. They are:
RFC 1155 which defines the SMI, the mechanisms used for describing
and naming objects for the purpose of management. RFC 1212
defines a more concise description mechanism, which is wholly
consistent with the SMI.
RFC 1156 which defines MIB-I, the core set of managed objects for
the Internet suite of protocols. RFC 1213, defines MIB-II, an
evolution of MIB-I based on implementation experience and new
operational requirements.
RFC 1157 which defines the SNMP, the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
T. Brown (editor) Expires 1/2/94 [Page 2]
Internet Draft Frame Relay Service MIB July 2, 1993
4. Objects
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) [7] defined in the SMI. In particular, each
object has a name, a syntax, and an encoding. The name is an
object identifier, an administratively assigned name, which
specifies an object type. The object type together with an
object instance serves to uniquely identify a specific
instantiation of the object. For human convenience, we often
use a textual string, termed the OBJECT DESCRIPTOR, to also
refer to the object type.
The syntax of an object type defines the abstract data
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [3]
purposely restricts the ASN.1 constructs which may be used.
These restrictions are explicitly made for simplicity.
The encoding of an object type is simply how that object type
is represented using the object type's syntax. Implicitly
tied to the notion of an object type's syntax and encoding is
how the object type is represented when being transmitted on
the network. The SMI specifies the use of the basic encoding
rules of ASN.1 [8], subject to the additional requirements
imposed by the SNMP.
4.1. Format of Definitions
Section 6 contains contains the specification of all object
types contained in this MIB module. The object types are
defined using the conventions defined in the SMI, as amended
by the extensions specified in RFC1212 [9].
T. Brown (editor) Expires 1/2/94 [Page 3]
Internet Draft Frame Relay Service MIB July 2, 1993
5. Overview
These objects are used when the particular media being used to
managed Frame Relay Service. At present, this applies to
these values of the ifType variable in the Internet-standard
MIB:
frame-relay-service (xx)
This section provides an overview and background of how to use
this MIB and other potential MIBs when managing a Frame Relay
Service.
The following diagram shows the MIB stack that could be
followed for managing a Frame Relay Service. This is only an
example and not meant to be inclusive.
_____________________________________
| |
| MIB II |
|___________________________________|
| | | |
| Frame Relay | SIP | RFC1294 |
| X.25 MIB | Relay | (no applic.|
| for IW/Encap.| MIB | MIB) |
| | | |
|-----------------------------------|
| |
| Frame Relay Service MIB |
|___________________________________|
| | |
| Physical Layer MIBs | ATM MIB |
| e.g., DS1/E1 MIB, |---------|
| RS232-like MIB | Phy. |
| | Layer |
| | MIB |
|-------------------------|---------|
SCOPE OF MIB:
The Frame Relay Service MIB will only manage the Frame Relay
portion of the network and will provide a pointer to the lower
layer MIB (for example, a physical layer MIB or the ATM MIB)
for each UNI/NNI logical port.
This MIB will NOT be implemented on User Equipment.
T. Brown (editor) Expires 1/2/94 [Page 4]
Internet Draft Frame Relay Service MIB July 2, 1993
Frame Relay Service SNMP MIB for Customer Network Management
(CNM) is an SNMPv1 MIB. It provides read-only information
that allows end-customers to obtain performance monitoring,
fault detection, and configuration information about their
Frame Relay Service. By using this and other related MIBs, a
customer's NMS can monitor their PVCs and UNI/NNI logical
ports. Internal aspects of the network (e.g., switching
elements, line cards, and network routing tables) are outside
the scope of this MIB. The Customer's NMS will be able to
access the SNMP proxy-agent within the Frame Relay network
using SNMP over UDP over IP with IP encapsulated in Frame
Relay according to RFC1294/ANSI T1.617 Annex F. The customer
thus has a PVC to the SNMP proxy-agent. Alternate access
mechanisms are possible. The initial implementation of the
MIB is based on SNMPv1. The service capabilities include
retrieving information and receiving TRAPs. It is beyond the
scope of this MIB to define managed objects to monitor the
physical layer. Existing physical layer MIBs (e.g., DS1 MIB)
and MIB II will be used as possible. The Frame Relay Service
SNMP MIB for CNM will not contain any managed objects to
monitor the physical layer. However, the Frame Relay Service
SNMP MIB for CNM will contain a pointer to the appropriate
lower layer MIB for each UNI/NNI logical port. To the maximum
extent as possible, PVCs and SVCs will be treated equally in
the MIB.
The Frame Relay Service MIB will only manage the Frame Relay
portion of the network and will provide a pointer to the lower
layer MIB (for example, a physical layer MIB or the ATM MIB)
for each UNI/NNI logical port.
This MIB is only used to manage a single Frame Relay Service
offering from one network. If the customer's PVCs traverse
multiple networks, then the customer needs to poll multiple
network agents to retrieve their end-to-end view of their
service. This MIB will be implemented on a proxy-agent
architecture within each Frame Relay Service network. See
Figure 1 and the Service Management Architecture [11].
5.1. Apply MIB II to a Frame Relay Service
Use the System Group to apply to the SNMP proxy-agent, since
the proxy-agent may be monitoring many Frame Relay devices in
one network. System Group applies to only one system. This
T. Brown (editor) Expires 1/2/94 [Page 5]
Internet Draft Frame Relay Service MIB July 2, 1993
group is not instantiated.
sysDescr: ASCII string describing the SNMP proxy-agent.
Can be up to 255 characters long. This field is
generally used to indicate the network providers
identification and type of service offered.
sysObjectID: Unique OBJECT IDENTIFIER (OID) for the SNMP proxy-agent.
sysUpTime: Clock in the SNMP proxy-agent; TimeTicks
in 1/100s of a second. Elapsed type since
the proxy-agent came on line.
sysContact: Contact for the SNMP proxy-agent.
ASCII string of up to 255 characters.
sysName: Domain name of the SNMP proxy-agent, for example,
acme.com
sysLocation: Location of the SNMP proxy-agent.
ASCII string of up to 255 characters.
sysServices: Services of the managed device. The value "2"
which implies that
the Frame Relay network is providing
a subnetwork level service is recommended.
This specifies how the Interfaces Group defined in MIB II
shall be used for the management of Frame Relay based
interfaces, and in conjunction with the Frame Relay Service
MIB module. This memo assumes the interpretation of the
Interfaces group to be in accordance with [10]: "The
interfaces table (ifTable) contains information on the managed
resource's interfaces. Each sub- layer below the internetwork
layer of a network interface is considered an interface."
Thus, the ifTable allows the following Frame Relay-based
interfaces to be represented as table entries:
- Frame Relay interfaces in the Frame Relay equipment (e.g.,
switches, routers or networks) with Frame Relay interfaces.
This level is concerned with generic frame counts and
not with individual virtual connections.
In accordance with the guidelines of ifTable, frame counts per
virtual connection are not covered by ifTable, and is
T. Brown (editor) Expires 1/2/94 [Page 6]
Internet Draft Frame Relay Service MIB July 2, 1993
considered interface specific and covered in the Frame Relay
Service MIB module. In order to interrelate the ifEntries
properly, the Interfaces Stack Group defined in [10] shall be
supported.
Some specific interpretations of ifTable for Frame Relay
follow.
Object Use for the generic Frame Relay layer
====== =========================================
ifIndex Each Frame Relay port is represented by an ifEntry.
ifDescr Description of the Frame Relay interface.
ASCII string describing the UNI/NNI access channel. Can be up to
255 characters long.
ifType The value to be allocated for Frame Relay Service is xx.
ifMtu Set to maximum frame size in octets for this frame relay port.
ifSpeed Peak bandwidth in bits per second available for use.
This could be the speed of the access channel and not
the access rate. Actual user information transfer rate (i.e., access rate of the
UNI or NNI access channel in bits per second (this is not the clocking
speed). For example, it is 1,536,000 bits per second for a
DS1-based UNI/NNI access
channel and 1,984,000 bits per second for an E1-based UNI/NNI access channel.
ifPhysAddress The primary address for this interface/port
assigned by the Frame Relay interface provider.
An octet string of zero length if no address is
used for this interface.
ifAdminStatus Supports read-only access (initially).
The desired administrative status of the frame relay port.
ifOperStatus The current operational status of the Frame Relay
UNI or NNI access channel.
ifLastChange The elapsed time since the last re-initialization of the port.
The value of sysUpTime at the time the interface entered
its current operational state. If the current state
was entered prior to
the last re-initialization of the local network
management subsystem, then
this object contains a zero value.
ifInOctets The number of received octets.
ifOutOctets The number of transmitted octets.
ifInUcastPkts The number of received unerrored frames.
ifInNUcastPkts Set to 0 since the generic Frame Relay level is
point-to-point.
ifOutUcastpkts The number of frames received for transmission.
[Ed. note: Frame Relay switches provide counts of
T. Brown (editor) Expires 1/2/94 [Page 7]
Internet Draft Frame Relay Service MIB July 2, 1993
transmitted frames and not of frames received
for transmission as required by the ifTable.
This is because the latter counter is
switch architecture dependent.
Comments are requested on this issue.]
ifOutNUcastpkts Set to 0 since the generic Frame Relay level is
point-to-point.
ifInErrors The number of received frames that are
discarded, because of an error. Possible errors can be
the following: the frame relay frames
were too long, had CRC errors, or were HDLC
aborts.
ifInUnknownProtos The number of received frames discarded
due to header content errors which include
unrecognized DLCI values or incorrect
header values.
ifInDiscards [to be specified]
ifOutErrors [to be specified]
ifOutDiscards [to be specified]
ifOutQLen [to be specified]
ifSpecific Set to the OBJECT IDENTIFIER { experimental 45 }.
Using the SNMP Group of MIB II is an implementation choice.
5.2. Frame Relay Service MIB Terminology
Access Channel - An access channel generically refers to the
DS1/E1 or DS3/E3-based UNI access channel or NNI access
channel across which frame relay data transits. An access
channel is the access pathway for a single stream of user
data.
Within a given T1 line, an access channel can denote any one
of the following:
o Unchannelized T1 - the entire T1 line is considered an access
channel. Each access channel is comprised of 24 T1 time slots.
o Channelized T1 - an access channel is any one of 24 channels.
Each access channel is comprised of a single T1 time slot.
o Fractional T1 - an access channel is a grouping of N T1 time
slots (NX56/64 Kbps, where N = 1-23 T1 Time slots per FT1 Access
T. Brown (editor) Expires 1/2/94 [Page 8]
Internet Draft Frame Relay Service MIB July 2, 1993
Channel) that may be assigned in consecutive or non-consecutive
order.
Within a given E1 line, a channel can denote any one of the following:
o Unchannelized E1 - the entire E1 line is considered a single
access channel. Each access channel is comprised of 31 E1 time
slots.
o Channelized E1 - an access channel is any one of 31 channels.
Each access channel is comprised of a single E1 time slot.
o Fractional E1 - an access channel is a grouping of N E1 time
slots (NX64 Kbps, where N = 1-30 E1 time slots per FE1 access
channel) that may be assigned in consecutive or non-consecutive
order.
Within a given unformatted line, the entire unformatted line
is considered an access channel. Examples include RS-232,
V.35, V.36 and X.21 (non- switched).
Access Rate - The data rate of the access channel. The speed
of the user access channel determines how rapidly the end user
can inject data into the network.
Bc - The Committed Burst Size (Bc) is the maximum amount of
subscriber data that the network agrees to transfer, under
normal conditions, during a time interval Tc. Bc is offered in
terms of bits.
Be - The Excess Burst Size (Be) is the maximum amount of
uncommitted data in excess of Bc that the network will attempt
to deliver during a time interval Tc. Be is offered in terms
of bits.
CIR - The Committed Information Rate (CIR) is the subscriber
data throughput that the network commits to supporting under
normal network conditions. CIR is averaged over the Committed
Rate Measurement Interval (Tc). CIR is offered in terms of
bits per second.
Permanent Virtual Connection (PVC) - A virtual connection that
has its endpoints and bearer capabilities defined at
subscription time.
T. Brown (editor) Expires 1/2/94 [Page 9]
Internet Draft Frame Relay Service MIB July 2, 1993
Time slot (E1) - An octet within the 256-bit information field
in each E1 frame is defined as a time slot. Time slots are
position sensitive within the 256-bit information field.
Fractional E1 service is provided in contiguous or non-
contiguous time slot increments.
Time slot (T1) - An octet within the 192-bit information field
in each T1 frame is defined as a time slot. Time slots are
position sensitive within the 192-bit information field.
Fractional T1 service is provided in contiguous or non-
contiguous time slot increments.
T. Brown (editor) Expires 1/2/94 [Page 10]
Internet Draft Frame Relay Service MIB July 2, 1993
+-------------------------------------+
| Customer Network Management Station |
| (SNMP based) |
+-------------------------------------+
/| /| /|
| | |
UNI / NNI / NNI / UNI
| +-----------+ | +-----------+ | +-----------+ |
| | | | | | | | | |
Originating | | | | | | | | | |Terminating
+--------+ | | Network I | | | Network J | | | Network K | | +--------+
| | | | | | | | | | | | | |
| User A | | | | | | | | | | | | |
| |----| |---| |---| |----| User B |
| | | | | | | | | | | | | |
| ////////////////////////////////////////////////////////////// |
| | | | | | | | | | | | | |
+--------+ | +-----------+ | +-----------+ | +-----------+ | +--------+
| | | |
| | | |
| PVC Segment 1 | PVC Segment 2 | PVC Segment 3 |
|<------------->|<------------->|<------------->|
| |
| Multi-network PVC |
|<--------------------------------------------->|
| NNI = Network-to Network Interface |
UNI = User-to-Network Interface
Figure 1
Multi-network PVC
T. Brown (editor) Expires 1/2/94 [Page 11]
Internet Draft Frame Relay Service MIB July 2, 1993
6. Object Definitions
RFCxxxx-MIB DEFINITIONS ::= BEGIN
IMPORTS
experimental, Counter, TimeTicks
FROM RFC1155-SMI
DisplayString
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212
TRAP-TYPE
FROM RFC-1215;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in RFC 1212.
frnetserv OBJECT IDENTIFIER ::= { experimental 45 }
T. Brown (editor) Expires 1/2/94 [Page 12]
Internet Draft Frame Relay Service MIB July 2, 1993
-- The Frame Relay Service Logical Port Group
-- Implementation of this group is mandatory for all systems
-- that perform Frame Relay Services.
-- This group has two tables:
-- Frame Relay Logical Port Information
-- Frame Relay Management VC Signaling Parameters and Errors
-- the Frame Relay Logical Port Information
frLportTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrLportEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The Frame Relay Logical Port Information table."
::= { frnetserv 1 }
frLportEntry OBJECT-TYPE
SYNTAX FrLportEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An entry in the Frame Relay Logical Port
Information table."
INDEX { frLportIfIndex }
::= { frLportTable 1 }
FrLportEntry ::=
SEQUENCE {
frLportIfIndex
INTEGER,
frLportNumPlan
INTEGER,
frLportNetAddress
OCTET STRING,
frLportContact
DisplayString,
frLportLocation
DisplayString,
frLportIfType
INTEGER,
frLportAddrDLCILen
T. Brown (editor) Expires 1/2/94 [Page 13]
Internet Draft Frame Relay Service MIB July 2, 1993
INTEGER,
frLportVCSigProtocol
INTEGER,
frLportVCSigPointer
OBJECT IDENTIFIER
}
frLportIfIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to MIB II's
ifIndex value for this UNI/NNI logical port."
::= { frLportEntry 1 }
frLportNumPlan OBJECT-TYPE
SYNTAX INTEGER {
e164(1),
x121(2),
private(3),
none(4)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the network
address numbering plan for this UNI/NNI logical
port. The value none implies that there is no
frLportNetAddress. The SNMP proxy-agent will
return an octet string of zero length for
frLportNetAddress."
::= { frLportEntry 2 }
frLportNetAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..20))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the UNI/NNI
logical port. It is typically a global address
for the UNI/NNI logical port that is assigned by
the service provider."
::= { frLportEntry 3 }
T. Brown (editor) Expires 1/2/94 [Page 14]
Internet Draft Frame Relay Service MIB July 2, 1993
frLportContact OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the network
contact for this UNI/NNI logical port."
::= { frLportEntry 4 }
frLportLocation OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the network
location for this UNI/NNI logical port."
::= { frLportEntry 5 }
frLportIfType OBJECT-TYPE
SYNTAX INTEGER {
uni(1),
nni(2)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the type of
network interface for this logical port."
::= { frLportEntry 6 }
frLportAddrDLCILen OBJECT-TYPE
SYNTAX INTEGER {
twoOctets10Bits(1),
threeOctets10Bits(2),
threeOctets16Bits(3),
fourOctets17Bits(4),
fourOctets23Bits(5)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Q.922
Address field length and DLCI length for this
UNI/NNI logical port."
::= { frLportEntry 7 }
T. Brown (editor) Expires 1/2/94 [Page 15]
Internet Draft Frame Relay Service MIB July 2, 1993
frLportVCSigProtocol OBJECT-TYPE
SYNTAX INTEGER {
none(1),
lmi(2),
ansiT1617D(3),
ansiT1617B(4),
ccittQ933A(5)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Local
In-Channel Signaling Protocol that is used for
this frame relay UNI/NNI logical port."
::= { frLportEntry 8 }
frLportVCSigPointer OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is used as a pointer to
the table that contains the Local In-Channel
Signaling Protocol parameters and errors for this
UNI/NNI logical port. See the Frame Relay
Management VC Signaling Parameters and Errors
Group."
::= { frLportEntry 9 }
T. Brown (editor) Expires 1/2/94 [Page 16]
Internet Draft Frame Relay Service MIB July 2, 1993
-- the Frame Relay Management VC Signaling Parameters and Errors
frMgtVCSigTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrMgtVCSigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The Frame Relay Management VC Signaling
Parameters and Errors table."
::= { frnetserv 2 }
frMgtVCSigEntry OBJECT-TYPE
SYNTAX FrMgtVCSigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An entry in the Frame Relay Management VC
Signaling Parameters Errors table."
INDEX { frMgtVCSigIfIndex }
::= { frMgtVCSigTable 1 }
FrMgtVCSigEntry ::=
SEQUENCE {
frMgtVCSigIfIndex
INTEGER,
frMgtVCSigProced
INTEGER,
frMgtVCSigUserN391
INTEGER,
frMgtVCSigUserN392
INTEGER,
frMgtVCSigUserN393
INTEGER,
frMgtVCSigUserT391
INTEGER,
frMgtVCSigNetN392
INTEGER,
frMgtVCSigNetN393
INTEGER,
frMgtVCSigNetT392
INTEGER,
frMgtVCSigNetnN4
INTEGER,
frMgtVCSigNetnT3
INTEGER,
T. Brown (editor) Expires 1/2/94 [Page 17]
Internet Draft Frame Relay Service MIB July 2, 1993
frMgtVCSigLinkRelRespErrors
Counter,
frMgtVCSigProtRespErrors
Counter,
frMgtVCSigInactiveResps
Counter,
frMgtVCSigLinkRelInitErrors
Counter,
frMgtVCSigProtInitErrors
Counter,
frMgtVCSigInactiveInits
Counter
}
frMgtVCSigIfIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to MIB II's
ifIndex value for this UNI/NNI logical port."
::= { frMgtVCSigEntry 1 }
frMgtVCSigProced OBJECT-TYPE
SYNTAX INTEGER {
u2nuser(1),
u2nnet(2),
bidirect(3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Local
In-Channel Signaling Procedure that is used for
this UNI/NNI logical port. The UNI/NNI logical
port can be performing user-to-network user-side
procedures, user-to-network network-side
procedures, or bidirectional procedures."
::= { frMgtVCSigEntry 2 }
frMgtVCSigUserN391 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
T. Brown (editor) Expires 1/2/94 [Page 18]
Internet Draft Frame Relay Service MIB July 2, 1993
"The value of this object identifies the User-side
N391 full status polling cycle value (nN1 for LMI)
for this UNI/NNI logical port. If the logical
port is not performing user-side procedures, then
this value is equal to zero. This applies to Q.933
Annex A, T1.617 Annex D and LMI."
DEFVAL { 6 }
::= { frMgtVCSigEntry 3 }
frMgtVCSigUserN392 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the User-side
N392 error threshold value (nN2 for LMI) for this
UNI/NNI logical port. If the logical port is not
performing user-side procedures, then this value
is equal to zero. This applies to Q.933 Annex A,
T1.617 Annex D and LMI."
DEFVAL { 3 }
::= { frMgtVCSigEntry 4 }
frMgtVCSigUserN393 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the User-side
N393 monitored events count value (nN3 for LMI)
for this UNI/NNI logical port. If the logical
port is not performing user-side procedures, then
this value is equal to zero. This applies to Q.933
Annex A, T1.617 Annex D and LMI."
DEFVAL { 4 }
::= { frMgtVCSigEntry 5 }
frMgtVCSigUserT391 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the User-side
T391 link integrity verification polling timer
value (nT1 for LMI) for this UNI/NNI logical port.
T. Brown (editor) Expires 1/2/94 [Page 19]
Internet Draft Frame Relay Service MIB July 2, 1993
If the logical port is not performing user-side
procedures, then this value is equal to zero. This
applies to Q.933 Annex A, T1.617 Annex D and LMI."
DEFVAL { 10 }
::= { frMgtVCSigEntry 6 }
frMgtVCSigNetN392 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Network-
side N392 error threshold value (nN3 for LMI) for
this UNI/NNI logical port. If the logical port is
not performing network-side procedures, then this
value is equal to zero. This applies to Q.933
Annex A, T1.617 Annex D and LMI."
DEFVAL { 3 }
::= { frMgtVCSigEntry 7 }
frMgtVCSigNetN393 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Network-
side N393 monitored events count value (nN3 for
LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to zero. This
applies to Q.933 Annex A, T1.617 Annex D and LMI."
DEFVAL { 4 }
::= { frMgtVCSigEntry 8 }
frMgtVCSigNetT392 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Network-
side T392 polling verification timer value (nT2
for LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to zero. This
applies to Q.933 Annex A, T1.617 Annex D and LMI."
T. Brown (editor) Expires 1/2/94 [Page 20]
Internet Draft Frame Relay Service MIB July 2, 1993
DEFVAL { 15 }
::= { frMgtVCSigEntry 9 }
frMgtVCSigNetnN4 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Network-
side nN4 maximum status enquires received value
for this UNI/NNI logical port. If the logical
port is not performing network-side procedures or
is not performing lmi procedures, then this value
is equal to zero. This applies only to LMI."
::= { frMgtVCSigEntry 10 }
frMgtVCSigNetnT3 OBJECT-TYPE
SYNTAX INTEGER (0..20)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the Network-
side nT3 timer (for nN4 status enquires received)
value for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures or is not performing lmi procedures,
then this value is equal to zero. This applies
only to LMI."
::= { frMgtVCSigEntry 11 }
frMgtVCSigLinkRelRespErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of local in-channel signaling link
reliability errors (responding to polls) for this
UNI/NNI logical port."
::= { frMgtVCSigEntry 12 }
frMgtVCSigProtRespErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
T. Brown (editor) Expires 1/2/94 [Page 21]
Internet Draft Frame Relay Service MIB July 2, 1993
"The number of local in-channel signaling protocol
errors (responding to polls) for this UNI/NNI
logical port."
::= { frMgtVCSigEntry 13 }
frMgtVCSigInactiveResps OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the channel declared inactive
(responding to polls) (i.e., N392 errors in N393
events) for this UNI/NNI logical port."
::= { frMgtVCSigEntry 14 }
frMgtVCSigLinkRelInitErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of local in-channel signaling link
reliability errors (initiating polls) for this
UNI/NNI logical port."
::= { frMgtVCSigEntry 15 }
frMgtVCSigProtInitErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of local in-channel signaling protocol
errors (initiating polls) for this UNI/NNI logical
port."
::= { frMgtVCSigEntry 16 }
frMgtVCSigInactiveInits OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the channel declared inactive
(initiating polls) (i.e., N392 errors in N393
events) for this UNI/NNI logical port."
::= { frMgtVCSigEntry 17 }
T. Brown (editor) Expires 1/2/94 [Page 22]
Internet Draft Frame Relay Service MIB July 2, 1993
-- The Frame Relay PVC Group
-- Implementation of this group is mandatory for all systems
-- that perform Frame Relay Services.
-- the Frame Relay PVC Information
frPVCTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrPVCEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The Frame Relay PVC table."
::= { frnetserv 3 }
frPVCEntry OBJECT-TYPE
SYNTAX FrPVCEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An entry in the Frame Relay PVC table."
INDEX { frPVCLocIfIndex, frPVCLocDLCIIndex }
::= { frPVCTable 1 }
FrPVCEntry ::=
SEQUENCE {
frPVCLocIfIndex
INTEGER,
frPVCLocDLCIIndex
INTEGER,
frPVCRemoteLport
INTEGER,
frPVCRemoteDLCI
INTEGER,
frPVCAdminStatus
INTEGER,
frPVCOperStatus
INTEGER,
frPVCLastChange
TimeTicks,
frPVCMaxFrameSize
INTEGER,
frPVCRcvdSigStatus
INTEGER,
frPVCUnitSize
T. Brown (editor) Expires 1/2/94 [Page 23]
Internet Draft Frame Relay Service MIB July 2, 1993
INTEGER,
frPVCInFrames
Counter,
frPVCOutFrames
Counter,
frPVCInDEFrames
Counter,
frPVCOutDEFrames
Counter,
frPVCInDiscards
Counter,
frPVCInUnits
Counter,
frPVCOutUnits
Counter,
frPVCBc
INTEGER,
frPVCBe
INTEGER,
frPVCCIR
INTEGER,
frPVCGenericPointer
OBJECT IDENTIFIER
}
frPVCLocIfIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to MIB II's
ifIndex value for this local UNI/NNI logical
port."
::= { frPVCEntry 1 }
frPVCLocDLCIIndex OBJECT-TYPE
SYNTAX INTEGER (1..8388608)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to the DLCI
value for this local UNI/NNI logical port PVC."
::= { frPVCEntry 2 }
frPVCRemoteLport OBJECT-TYPE
T. Brown (editor) Expires 1/2/94 [Page 24]
Internet Draft Frame Relay Service MIB July 2, 1993
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to MIB II's
ifIndex value for the remote UNI/NNI logical port.
If the value is equal to zero, then this remote
logical port is not a frame relay UNI/NNI logical
port."
::= { frPVCEntry 3 }
frPVCRemoteDLCI OBJECT-TYPE
SYNTAX INTEGER (0..8388608)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to the DLCI
value for the remote UNI/NNI logical port PVC. If
the value is equal to zero, then this is not a
frame relay PVC."
::= { frPVCEntry 4 }
frPVCAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
testing(4)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the desired
administrative status of this UNI/NNI logical port
PVC. This state is set by an administrative
entity."
::= { frPVCEntry 5 }
frPVCOperStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
testing(4)
}
T. Brown (editor) Expires 1/2/94 [Page 25]
Internet Draft Frame Relay Service MIB July 2, 1993
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the current
operational status of this UNI/NNI logical port
PVC."
::= { frPVCEntry 6 }
frPVCLastChange OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime at the time the PVC
entered its current operational state. If the
current state was entered prior to the last re-
initialization of the proxy-agent, then this
object contains a zero value."
::= { frPVCEntry 7 }
frPVCMaxFrameSize OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is the size in octets of
the largest frame relay information field for this
PVC in the ingress direction (into the frame relay
network from the local logical port's point of
view). Must be less than or equal to the
corresponding ifMtu for this frame relay UNI/NNI
logical port."
::= { frPVCEntry 8 }
frPVCRcvdSigStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
none(4)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the PVC
T. Brown (editor) Expires 1/2/94 [Page 26]
Internet Draft Frame Relay Service MIB July 2, 1993
status received via the local in-channel signaling
procedures for this UNI/NNI logical port PVC.
This object is only is only pertinent for
bidirectional procedures and user-to-network user
side procedures. For user-to-network network side
procedures, the value of this object should be
none."
::= { frPVCEntry 9 }
frPVCUnitSize OBJECT-TYPE
SYNTAX INTEGER (1..1024)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the the unit
size for this UNI/NNI logical port PVC. The unit
size is equal to a block of octets. This object
is used to indicate that for this UNI/NNI logical
port PVC the Frame Relay network service can only
resolve the frPVCInUnits and frPVCOutUnits to this
value of frPVCUnitSize. The default value is 1."
DEFVAL { 1 }
::= { frPVCEntry 10 }
frPVCInFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of frames received by the network
(ingress) for this UNI/NNI logical port PVC. This
includes any frames discarded by the network due
to submitting more than Bc + Be data or due to any
network congestion recovery procedures."
::= { frPVCEntry 11 }
frPVCOutFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of frames sent by the network (egress)
regardless of whether they are Bc or Be frames for
this UNI/NNI logical port PVC."
::= { frPVCEntry 12 }
T. Brown (editor) Expires 1/2/94 [Page 27]
Internet Draft Frame Relay Service MIB July 2, 1993
frPVCInDEFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of frames received by the network
(ingress) for this UNI/NNI logical port PVC which
were treated as excess traffic. Frames which are
sent to the network with DE set to zero are
treated as excess when more than Bc bits are
submitted to the network during the Committed Rate
Measurement Interval (Tc). Excess traffic may or
may not be discarded at the ingress if more than
Bc + Be bits are submitted to the network during
Tc. Traffic discarded at the ingress is not
recorded in frPVCInDeFrames. Frames which are
sent to the network with DE set to one are also
treated as excess."
::= { frPVCEntry 13 }
frPVCOutDEFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of frames sent by the network (egress)
that were observed to have the DE bit set to one
for this UNI/NNI logical port PVC."
::= { frPVCEntry 14 }
frPVCInDiscards OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of frames received by the the network
(ingress) that were discarded due to traffic
enforcement for this UNI/NNI logical port PVC."
::= { frPVCEntry 15 }
frPVCInUnits OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
T. Brown (editor) Expires 1/2/94 [Page 28]
Internet Draft Frame Relay Service MIB July 2, 1993
"The number of units received by the network
(ingress) for this UNI/NNI logical port PVC. If
the frPVCUnitSize is equal to one, then this
object counts octets. This counter should only
count units from the beginning of the frame relay
header field to the end of user data."
::= { frPVCEntry 16 }
frPVCOutUnits OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of units sent by the network (egress)
for this UNI/NNI logical port PVC. If the
frPVCUnitSize is equal to one, then this object
counts octets. This counter should only count
units from the beginning of the frame relay header
field to the end of user data."
::= { frPVCEntry 17 }
frPVCBc OBJECT-TYPE
SYNTAX INTEGER (0..4294967295)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to the
committed burst size (Bc) parameter (measured in
bits) in the ingress direction for this UNI/NNI
logical port PVC."
::= { frPVCEntry 18 }
frPVCBe OBJECT-TYPE
SYNTAX INTEGER (0..4294967295)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to the excess
burst size (Be) parameter (measured in bits) in
the ingress direction for this UNI/NNI logical
port PVC."
::= { frPVCEntry 19 }
frPVCCIR OBJECT-TYPE
SYNTAX INTEGER (0..4294967295)
T. Brown (editor) Expires 1/2/94 [Page 29]
Internet Draft Frame Relay Service MIB July 2, 1993
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is equal to the
committed information rate (CIR) parameter
(measured in bits per second) in the ingress
direction for this UNI/NNI logical port PVC."
::= { frPVCEntry 20 }
frPVCGenericPointer OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is used as a pointer to
the Generic PVC Table. This OID should contain the
appropriate ifIndex and vcIndex values for the
Generic PVC Table."
::= { frPVCEntry 21 }
T. Brown (editor) Expires 1/2/94 [Page 30]
Internet Draft Frame Relay Service MIB July 2, 1993
-- Frame Relay Network Service TRAPS
frPVCStatusChange TRAP-TYPE
ENTERPRISE frnetserv
VARIABLES { frPVCLocIfIndex, frPVCLocDLCIIndex, frPVCOperStatus,
frPVCRcvdSigStatus }
DESCRIPTION
"This trap indicates that the indicated PVC has
changed state."
::= 1
END
T. Brown (editor) Expires 1/2/94 [Page 31]
Internet Draft Frame Relay Service MIB July 2, 1993
7. Acknowledgments
This document was produced by the Frame Relay Service MIB
Working Groups:
Special thanks goes to the Frame Relay Forum Technical
Committee for its participation in writing this MIB.
T. Brown (editor) Expires 1/2/94 [Page 32]
Internet Draft Frame Relay Service MIB July 2, 1993
8. References
[1] Cerf, V., "IAB Recommendations for the Development of Internet
Network Management Standards", RFC 1052, NRI, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management
Review Group", RFC 1109, NRI, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[4] McCloghrie K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets", RFC 1156, Hughes
LAN Systems, Performance Systems International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", RFC 1157, SNMP Research,
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[6] McCloghrie K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets", RFC 1213,
Performance Systems International, March 1991.
[7] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International
Standard 8824, December 1987.
[8] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
[9] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems,
March 1991.
[10] K. McCloghrie and F. Kastenholz, Evolution of Interfaces
Group of MIB-II, Internet Draft, May, 1993.
[11] K. R. Rodemann, Service Management Architecture for Virtual Connection Services,
Internet-Draft, July 1993.
T. Brown (editor) Expires 1/2/94 [Page 33]
Internet Draft Frame Relay Service MIB July 2, 1993
9. Security Considerations
Security issues are not discussed in this memo.
10. Authors' Addresses
Tracy A. Brown
Bell Communications Research
331 Newman Springs Road
P.O. Box 7020
Red Bank, NJ 07701-7020
Phone: (908) 758-2107
EMail: tacox@mail.bellcore.com
T. Brown (editor) Expires 1/2/94 [Page 34]
Internet Draft Frame Relay Service MIB July 2, 1993
Table of Contents
1 Status of this Memo ................................... 1
2 Abstract .............................................. 1
3 The Network Management Framework ...................... 2
4 Objects ............................................... 3
4.1 Format of Definitions ............................... 3
5 Overview .............................................. 4
5.1 Apply MIB II to a Frame Relay Service ............... 5
5.2 Frame Relay Service MIB Terminology ................. 8
6 Object Definitions .................................... 12
6.1 The Frame Relay Service Logical Port Group .......... 13
6.1.1 The Frame Relay Logical Port Information .......... 13
6.1.2 The Frame Relay Management VC Signaling Parame-
ters and Errors .................................... 17
6.2 Frame Relay PVC Group ............................... 23
7 Acknowledgments ....................................... 32
8 References ............................................ 33
9 Security Considerations ............................... 34
10 Authors' Addresses ................................... 34
T. Brown (editor) Expires 1/2/94 [Page 35]